Kafka stacks locally through kubectl port-forward, in Docker #267
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
First automated build |
|
Built |
|
Actually |
solsson
added a commit
that referenced
this pull request
May 3, 2019
solsson
added a commit
to solsson/kafka-keyvalue
that referenced
this pull request
May 26, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Started as a CI experiment, but looked promising enough for all kinds of experiments with different Kafka stacks. Builds upon #253 #266. For example we could automate Prometheus setup and evaluate #259 with Grafana dashboard.
On my machine it takes about 2 minutes to go from nothing to a running Kafka stack. Note however that according to
docker statsthekafka-control-planecontainer takes 2.2 GB of memory and ~50% of a CPU core. I still think it's a lot lighter than on minikube.While this is an experiment I wanted everything contained within the dockerfile, hence the odd documentation/script setup.